Systems and methods for providing targeted content across user channels

ABSTRACT

A method of providing targeted content across user channels includes receiving a plurality of device activity events on a user device, storing the received plurality of device activity events, creating an audience population based on the stored device activity events, determining links for additional secondary user devices based on the user device, creating a cross-channel advertising campaign targeting the determined audience population, and running the cross-channel advertising campaign based on the device activity and the determined additional secondary user devices.

TECHNICAL FIELD

Various embodiments of the present disclosure relate generally toproviding targeted messages to users and, more particularly, toproviding such messages across user channels based on a user's onlineactivity on multiple devices and the user's inbound and outboundtelephone call activity.

BACKGROUND

In recent years, people have started spending more and more timebrowsing content on the Internet, as opposed to traditional sources. Asa result, the value of advertising on web pages has risen significantly,and techniques for targeting demographics of interest have become veryadvanced.

Advertising networks typically have hundreds or thousands of partners(often referred to as “publishers”) that publish online content alongwith “ad tags” provided by their partner ad network. For example, eachof a news website (www.news.com), a blog (www.blog.com), and aninformational website (www.info.com), among others, may engage an adnetwork to efficiently and profitably advertise to those websites'viewers. The ad network provides each of those sites with an ad taghaving the ad network's domain, e.g., “adnetwork.com.” For any visitors,or more specifically, visitors' browsers that allow third party cookies,the ad network may access cookie data of visitors to its partners' sites(i.e., across its entire network of sites), even though those sites'domains (e.g., www.news.com, etc.) do not match the ad network's domain.Specifically, the ad network's ad tag on each site may access cookiedata associated with the domain of the ad tag. As a result, the adnetwork may learn more about a user's browsing history across itsnetwork, and therefore more about the user's likely demographics,interests, purchasing goals, and other useful advertising information.

However, such advertising models and the use of cookies on a particulardevice may not allow an advertiser or other content provider to targetcontent to a user based on the user's online activity across multipledevices or the user's inbound and outbound telephone call activity.

The present disclosure is directed to overcoming one or more of theseabove-referenced challenges.

SUMMARY OF THE DISCLOSURE

According to certain aspects of the disclosure, systems and methods aredisclosed for providing targeted content across user channels.

In one embodiment, a computer-implemented method is disclosed forproviding targeted content across user channels. The method includesreceiving a plurality of device activity events on a user device,storing the received plurality of device activity events, creating anaudience population based on the stored device activity events,determining links for additional secondary user devices based on theuser device, creating a cross-channel advertising campaign targeting thedetermined audience population, and running the cross-channeladvertising campaign based on the device activity and the determinedadditional secondary user devices.

According to certain aspects of the disclosure, non-transitory computerreadable media are disclosed storing a program causing a computer toexecute a method of providing targeted content across user channels. Onemethod comprises: receiving a plurality of device activity events on auser device, storing the received plurality of device activity events,creating an audience population based on the stored device activityevents, determining links for additional secondary user devices based onthe user device, creating a cross-channel advertising campaign targetingthe determined audience population, and running the cross-channeladvertising campaign based on the device activity and the determinedadditional secondary user devices.

In accordance with another embodiment, a system is disclosed forproviding targeted content across user channels. The system comprises: amemory having processor-readable instructions stored therein; and aprocessor configured to access the memory and execute theprocessor-readable instructions, which when executed by the processorconfigures the processor to perform a plurality of functions, includingfunctions to: receive a plurality of device activity events on a userdevice, store the received plurality of device activity events, creatingan audience population based on the stored device activity events,determine links for additional secondary user devices based on the userdevice, create a cross-channel advertising campaign targeting thedetermined audience population, and run the cross-channel advertisingcampaign based on the device activity and the determined additionalsecondary user devices.

Additional objects and advantages of the disclosed embodiments will beset forth in part in the description that follows, and in part will beapparent from the description, or may be learned by practice of thedisclosed embodiments. The objects and advantages of the disclosedembodiments will be realized and attained by means of the elements andcombinations particularly pointed out in the appended claims. As will beapparent from the embodiments below, an advantage to the disclosedsystems and methods is that an advertiser or other content provider totarget content to a user based on the user's online activity acrossmultiple devices or the user's inbound and outbound telephone callactivity. The disclosed systems and methods discussed below may allowexpedited customer relationship management, improved recipient responserate, and enhanced revenue from channels not previously available.

It is to be understood that both the foregoing general description andthe following detailed description are exemplary and explanatory onlyand are not restrictive of the disclosed embodiments, as claimed.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute apart of this specification, illustrate various exemplary embodiments andtogether with the description, serve to explain the principles of thedisclosed embodiments.

FIG. 1 is a series of schematic diagrams depicting exemplaryenvironments in which users may use disclosed devices and methodsaccording to one or more embodiments.

FIG. 2 depicts a schematic diagram of an exemplary environment andsystem for synchronizing user advertising IDs across devices andbrowsers, according to one or more embodiments.

FIG. 3 depicts a flowchart of a method for synchronizing useradvertising IDs across devices and browsers, according to one or moreembodiments.

FIG. 4 depicts a flowchart of a method for performing Internetadvertising techniques based on user advertising IDs synchronized acrossdevices and browsers, according to one or more embodiments.

FIG. 5 is a schematic diagram of a flow for performing Internetadvertising techniques based on user advertising IDs synchronized acrossdevices and browsers, according to one or more embodiments.

FIG. 6 depicts a flowchart of a method of providing targeted contentacross user channels, according to one or more embodiments.

FIG. 7 depicts an exemplary device in which one or more embodiments maybe implemented.

FIGS. 8A-8C depict example user interfaces providing targeted contentacross user channels, according to one or more embodiments.

DETAILED DESCRIPTION OF EMBODIMENTS

Various embodiments of the present disclosure relate generally toproviding targeted messages to users.

The terminology used below may be interpreted in its broadest reasonablemanner, even though it is being used in conjunction with a detaileddescription of certain specific examples of the present disclosure.Indeed, certain terms may even be emphasized below; however, anyterminology intended to be interpreted in any restricted manner will beovertly and specifically defined as such in this Detailed Descriptionsection.

User activity by which users access the Internet may be considered to beone channel of user activity. Other type of activity, such as placing orreceiving telephone calls using a mobile device may be considered to bea different channel of user activity. According to one or embodiments,activity in one channel may be used to serve ads on a user's device in adifferent channel. For example, a user's Internet activity such as, forexample, browsing history, demographic data, behavioral information,user profiling information, purchase history, etc., may be used to serveads on a user's mobile device when placing or receiving a telephonecall.

For the user, such advertisements or targeted messages may providebenefits such as, for example, enhanced inbound call transparency, callblocking, flagging of fraudulent, unsolicited calls, faster, moreinteractive experience than voicemail, etc. For the advertiser ororiginator of the advertisement or targeted message, such advertisementsor targeted messages may provide benefits such as, for example,expedited customer relationship management, improved recipient responserate, and enhanced revenue from channels not previously available.

Such advertisements or targeted messages may be employed i variousscenarios such as: a credit card provider driving new card activations,a cruise line selling remnant cruise inventory, a pharmacy notifying auser of prescription refills, a car dealer service department remindingcustomers of service due or completed, survey, market research andpolling firms contacting potential participants, a retailer calls acustomer to confirm an order and schedule a deliver, a utility companycalls a customer to notify of an account balance due, etc.

By providing targeted content across user channels, advertisers andmerchants may engage with existing or new clients, may benefit fromimproved client interaction, and may access new channels for engagingnew or existing customers. Such communications may replace thesignificantly more intrusive alternative of having to speak to arepresentative, and, thus, improving the customer experience. Suchcommunications may also be more likely to influence the recipient'sbehavior than a digital advertisement impression, thus, potentiallyyielding higher response rate. Such communications may further improvecall center efficiency by obviating the need for customers to speakdirectly to recipient.

FIG. 1 is a schematic diagram of a series of environments in which usersmay access Internet content and advertising, according to exemplaryembodiments of the present disclosure. Specifically, FIG. 1 depicts howthe same user 100 may access the Internet using any number or type ofInternet-enabled devices, such as, for example, a mobile device 102(e.g., smartphone, PDA, etc.), a work computer 104 (e.g., such as a PC,Windows, Mac, etc., whether desktop or laptop), a home computer 106(e.g., a PC or Mac laptop or desktop), an automobile computer 108 (e.g.,whether OEM or after-market), a tablet 110, or any other type of kiosk,computer, or mobile device connected to the Internet through a wired orwireless connection. For example, a typical user might wake up in themorning and check the weather and his or her e-mail on his or hersmartphone 102. The user may then drive to work and access Internetcontent, such as traffic or news, through his or her automobile computer108. The user may then operate a computer 104 upon arriving at his orher workplace, including to access Internet content, whether related towork activities and/or personal activities. The user may then returnhome in the evening and use one or more of a home computer 106 and atablet 110. Of course, the preceding scenario is only exemplary innature, and users' Internet habits may vary widely in terms of whichdevices they use at given locations and times. For example, many usersmay use a tablet 110 only at work or only at home, while other users mayuse a tablet 110 while at home and at work, and for both personal andprofessional activities. Likewise, some users may use a mobile device102 to access both personal and professional Internet content and e-mailthroughout the day, even while also using a work computer 104. Inaddition, some users may use a mobile device 102 to place and receivetelephone calls throughout the day, even while also using a workcomputer 104 or other type of Internet-enabled device. Also, a user mayuse a home computer 106 at non-traditional times of the day, and may usethe home computer 106 to perform professional activities, whether duringthe day or evening.

FIG. 2 illustrates an exemplary environment in which users may accessthe Internet using multiple devices, including a plurality of userdevices 102-110. FIG. 2 also illustrates an exemplary system forsynchronizing user advertising IDs across devices and browsers, thesystem including one or more of: publisher servers 112, advertiserservers 114, and synchronization server systems 150, all disposed incommunication with the Internet 101. In one embodiment, publisherservers 112 and advertiser servers 114 may be owned and operated bypublishing and advertising entities, respectively, and not strictly partof the same system as synchronization server systems 150.

In one embodiment, user devices 102-110 may be owned and used by one ormore people, who may be viewers of web pages over the Internet, eitherthrough a mobile browser or web browser stored on respective userdevices. As described above, user devices 102-110 may include any typeof electronic device configured to send and receive data, such aswebsites and electronic advertisements, over the Internet. For example,each of user devices 102-110 may include a server, personal computer,tablet computer, mobile device, smartphone, and/or personal digitalassistant (“PDA”) disposed in communication with the Internet. Inaddition, mobile device or smartphone 102 may also be used to place andreceive telephone calls. Each of user devices 102-110 may have a webbrowser or mobile browser installed for receiving and displaying weband/or ad content from web servers. Thus, each of user devices 102-110may be configured to receive and display data that is received from oneor more of publisher servers 112, advertiser servers 114, andsynchronization server systems 150, among any other web servers, domainname system (“DNS”) servers, content distribution network (“CDN”)servers, etc., over the Internet. As described above, in one embodiment,a user may own and, simultaneously or intermittently, use one or more ofuser devices 102-110, whether of similar or different type.

Publisher web servers 112 may be owned and/or operated by any entitieshaving inventories of available online advertising space. For example,publishers may include online content providers, search engines, e-mailprograms, or any other online site or program having online usertraffic. Publishers may interact with user devices 102-110, advertiserservers 114, and synchronization server systems 150, through publisherservers 112 connected to the Internet. Thus, publishers may be able tocommunicate inventory information, such as site information, demographicinformation, cost information, etc., to other entities in theenvironment of FIG. 2.

Advertiser servers 114 may be owned and/or operated by any entitieshaving content, such as online advertisements (e.g., display ads, bannerads, pop-ups, etc.) desired to be delivered to online users. Advertisersmay interact with user devices 102-110, publisher servers 112, and/orsynchronization server systems 150, through advertiser servers 114connected to the Internet 101. Thus, advertisers may be able tocommunicate advertising information, such as ad information, targetinginformation, consumer information, budget information, biddinginformation, etc., to other entities in the environment of FIG. 2.

Synchronization server systems 150 may be configured to interact withone or more of user devices 102-110, publisher servers 112, andadvertiser servers 114 over the Internet 101 to perform any of thepresently disclosed techniques and methods. In one embodiment,synchronization server systems 150 may include one or more of: aplurality of ad servers 152, synchronization processor(s) 154, anddatabase(s) 156. Of course, it should be appreciated that ad servers 152may be operated by an operator only contractually or even looselyaffiliated with an operator of synchronization processor 154.Alternatively, the ad servers 152 and synchronization processor 154 maybe operated by the same advertising entity or online entity.

Ad servers 152 may include any type of servers configured to processadvertising information from advertisers and/or site information frompublishers, and send and receive ad requests and information from userdevices 102-110, either directly or indirectly. In one embodiment, adservers 152 may be owned and operated by an ad network, which may be abusiness that receives ad buys from advertisers, and serves ads oninventory supplied by publishers. Thus, an ad network operating adservers 152 may receive revenue from advertisers, purchase impressionsfrom publishers, and serve ads on publishers' web pages when viewersassociated with user devices 102-110 view those web pages. According toaspects of the present disclosure, ad servers 152 may be configured tointeract with synchronizing processor 154, such as through one or moreAPIs associated with synchronizing processor 154, to obtain one or moreof: unique user IDs, cookie data, browsing history, demographic data,user profile data, etc., in response to interaction from user devices102-110.

In certain embodiments, ad servers 152 may be remote web servers thatreceive advertising information from advertisers and serve ads to beplaced by publishers. Ad servers 152 may be configured to serve adsacross various domains of publishers, for example, based on advertisinginformation provided by advertisers. Ad servers 152 may also beconfigured to serve ads based on contextual targeting of web sites,search results, and/or user profile information. In some embodiments, adservers 152 may be configured to serve ads based on ad tags served byadvertiser servers 114 and/or publisher servers 112, and on ad requestsreceived from user devices 102-110. Ad servers 152 may be configured tosend and receive data from user devices 102-110, publisher servers 112,advertiser servers 114, and/or synchronizing processor 154, over theInternet.

Ad servers 152 and synchronizing processor 154, either alone or incombination, may include any type or combination of computing systems,such as clustered computing machines and/or servers. In one embodiment,each of ad servers 152 and synchronizing processor 154 may be anassembly of hardware, including a memory, a central processing unit(“CPU”), and/or a user interface. The memory may include any type of RAMor ROM embodied in a physical storage medium, such as magnetic storageincluding floppy disk, hard disk, or magnetic tape; semiconductorstorage such as solid state disk (SSD) or flash memory; optical discstorage; or magneto-optical disc storage. The CPU may include one ormore processors for processing data according to instructions stored inthe memory. The functions of the processor may be provided by a singlededicated processor or by a plurality of processors. Moreover, theprocessor may include, without limitation, digital signal processor(DSP) hardware, or any other hardware capable of executing software. Theuser interface may include any type or combination of input/outputdevices, such as a display monitor, touchpad, touchscreen, microphone,camera, keyboard, and/or mouse.

Regardless of specific physical components or layout, one or more of adservers 152 and synchronizing processor 154, or any other servers orsystems associated with ad network involving ad servers 152 andsynchronizing processor 154, may be programmed with instructions toperform a method of synchronizing user advertising IDs across devicesand browsers, and performing online targeted and behavioral advertisingacross user devices, according to the exemplary disclosed methods, suchas the exemplary methods described with respect to FIGS. 3-5 below.

FIG. 3 is a schematic diagram of the flow of information betweenentities for synchronizing user advertising IDs across devices andbrowsers, and performing online targeted and behavioral advertisingacross user devices, according to an exemplary embodiment of the presentdisclosure. Specifically, according to embodiments of the presentdisclosure, user devices 102-110, publisher servers 112, advertiserservers 114, and ad servers 152, may exchange data with one or more ofsynchronizing processor 154 and databases 156 of synchronization serversystems 150 (all through one or more computers and/or servers connectedto the Internet 101, as described with respect to FIG. 2).

Specifically, FIG. 3 depicts a method 300 for synchronizing useradvertising IDs across devices and browsers. In one embodiment, method300 may include determining whether a user's browser enables localstorage. If so, method 300 may include creating in the user's browser asandbox stored in the local storage system and registered to theadvertising system (e.g., a network associated with ad servers 152and/or synchronizing server system 150) (step 302).

Method 300 may also include creating and storing a unique identifier forthe user in the created sandbox (step 304). For example, method 300 mayinclude generating a unique ID that will be used to reference the userassociated with the device in which the sandbox was created, as well asother devices that the user uses to access the Internet. In oneembodiment, a unique ID may be any type of numeric or alpha-numericidentifier that can uniquely identify one user from another. In oneembodiment, the unique ID may be stored in database 156 and indexed orotherwise related to a profile of information known about the usermatching the unique ID.

Method 300 may also include optionally creating and storing an instanceidentifier specific to each of the user's devices (step 306). Forexample, if it is desirable to know—not only that a user is visitingcertain sites or taking certain actions using multiple devices—but also,which device the user was using during those site visits or, in oneembodiment, an instance identifier may be associated with each device,and web browsing history and actions may be stored in relation to theinstance identifier. In another embodiment, database 156 may store atable or index containing a unique identifier for each user, and aplurality of instance identifiers indexed or related to the uniqueidentifier, each instance identifier being indexed or related to adevice of the user.

Method 300 may also include replicating data created in the sandboxacross multiple browsers and local drives of the user's connecteddevices (step 308). For example, in some embodiments, where a user isusing a browser that enables users to log-in or otherwise authenticate,and enables synchronizing local storage data remotely (i.e., “in thecloud”), that remotely stored data may be synchronized or replicatedacross all devices in which a user has logged-in or authenticated intosuch a browser.

FIG. 4 is a flow diagram of a method for performing Internet advertisingtechniques based on user advertising IDs being synchronized acrossdevices and browsers, according to an exemplary embodiment of thepresent disclosure. Specifically, FIG. 4 depicts a method 400 forexecuting techniques between ad servers 152, synchronizing processor154, and/or databases 156 of synchronizing server systems 150 toadvertise to users based on data collected across a plurality of devicesthey may use.

In one embodiment, method 400 may include receiving, from a publisher, arequest for an advertisement, the request including a unique identifierand/or instance identifier for a user or the user's device (step 402).While an ad request may be received from a publisher, an ad request mayalternatively or additionally be received from the user or from theuser's device. Specifically, an ad server 152 may receive a request todeliver an ad or ad tag to a user upon the user requesting and/orvisiting a web page hosted on a publisher server 112. In one embodiment,the ad request may include the unique ID assigned to the user, theinstance ID assigned to the user's device, and/or cookie data containingone or both of the unique ID and the instance ID. As described abovewith respect to FIG. 3, the unique ID and/or instance ID may have beenreplicated through remote storage (e.g., cloud computing), across localstorage of a plurality of the user's devices.

Method 400 may further include receiving, based on the unique identifierand/or instance identifier, a demographic or browsing historyinformation generated from the user's use of a first device (step 404).Upon receiving the unique identifier and/or instance identifier, an adserver 152 and/or synchronizing processor 154 of the synchronizingserver 150 may lookup demographic and/or browsing history informationgenerated from the user's use of a first device. For example, the adserver 152 and/or synchronizing processor 154 may search databases 156for the unique identifier and/or instance identifier to find indexedbrowsing history, demographic data, behavioral information, userprofiling information, purchase history, etc. The stored historical datamay be data generated from the user's first device or any other devicehaving local storage containing the unique identifier and/or instanceidentifier.

Method 400 may further include determining, based on the demographic orbrowsing history information generated from the user's use of the firstdevice, an advertisement to display to the user during the user's use ofa second device (step 406). Specifically, when a user uses a seconddevice to request web content, e.g., from a publisher server 112, theuser's second device may also request an ad from an ad server 152.Because the user's second device may send an ad request containing theuser's unique identifier or instance identifier, the ad servers 152and/or synchronizing processor 154 may again lookup demographic orbrowsing history information generated from the user's use of a firstdevice. For example, the ad server 152 and/or synchronizing processor154 may search databases 156 for the unique identifier and/or instanceidentifier to find indexed browsing history, demographic data,behavioral information, user profiling information, purchase history,etc. The stored historical data may be data generated from the user'sfirst device or any other device having local storage containing theunique identifier and/or instance identifier. As a result, the adservers 152 and/or synchronizing processor 154 may be able to serve adson the user's device based on one or more of: browsing history,demographic data, behavioral information, user profiling information,purchase history, any or all of which may be based on data collectedfrom more than one device used by the user.

In general, publishers 112 may host websites having web pages thatdisplay content and advertising. In general, when a user uses a device102-110 to visit a web page hosted on a publisher server 112, thepublisher may send an impression request to an ad network, in this case,an ad server 152. In the impression request, the publisher 112 mayrequest an advertisement to display to the visiting user. The impressionrequest may include any data elements normally included in an impressionrequest, such as information about the web page, the publisher, and/orthe visiting user. The advertising system may select an advertisementfor the publisher to display based on an algorithm that considers thereceived information about the web page, the publisher, and/or thevisiting user. Thus, the Internet advertising system may, consistentwith its ad bidding and exchange techniques and various business rules,award impressions of ads to impression requests from publisher servers112. In other words, the Internet advertising system, through ad servers152, may cause ads received from advertiser servers 114 to be displayedon web pages hosted on publisher servers 112 when users devices 102-110request those web pages. Of course, as discussed above, the display ofthe ads may be precisely targeted both to the identities of the usersand publishers of servers 112, and the content of the publisher's webpage. For example, the Internet advertising system may select fordisplay the ad that is most likely to generate a strong and favorablereaction from the visiting user, based on assumptions, historical data,and statistics gathered about the publisher's site and the user.

FIG. 5 is a schematic diagram of a flow for performing Internetadvertising techniques based on user advertising IDs synchronized acrossdevices and browsers, according to an exemplary embodiment of thepresent disclosure. Specifically, FIG. 5 depicts the flow of requestsbetween a user's first device 502 and an ad or publisher server 506 andan ad or synchronizing server 510. FIG. 5 also depicts the flow ofrequests between a user's second device 504 and an ad or publisherserver 508 and an ad or synchronizing server 510.

As described above, the user's first device 502 and second device 504may be any type of device 102-110 described with respect to FIGS. 1 and2. Also, it should be appreciated that any number of devices may beapplicable within the scope of the description of FIG. 5. In addition,it should be appreciated that, although depicted as different, ad orpublisher servers 506, 508 may optionally be the same server; andalthough depicted as a single server system, ad or synchronizingserver(s) 510 may be separate and distinct servers accessed by theuser's multiple devices, such as devices 502, 504. In one embodiment,the ad or publisher servers 506, 508 may correspond to publisher oradvertiser servers 112, 114, and/or the ad or synchronizing server(s)510 may correspond to the ad servers 152, synchronizing processor 154,and/or databases 156 of synchronizing server system 150.

As shown in FIG. 5, in one embodiment, the user's first device 502 may(1) request a web page or ad from an ad or publisher server 506; and (2)receive HTTP and an ad tag from the ad or publisher server 506. Theuser's first device 502 may execute the ad tag, such as by executing anytype of client side script (e.g., JavaScript) to (3A) look-up a uniqueID stored on the device. As described above, the unique ID may be storedwithin local storage associated with a browser of the device 502. Theuser's first device 502 may then (4A) issue an ad request to ad orsynchronizing servers 510, where the request includes the looked-upunique ID. As an alternative to transmitting the unique ID in an adrequest, the user device 502 may (3B) set a cookie containing the uniqueID in location storage, and then (4B) issue an ad request to ad orsynchronizing servers 510, where the ad request includes cookie datathat may or may not include the unique ID. In one embodiment, the setcookie may include another type of advertising identifier that iscross-referenced to the user through the unique ID.

The ad or synchronizing servers 510 may then store any data relating tothe user of the user device 502 in relation to a cookie ID or unique ID,such as browsing history, demographic data, behavioral information, userprofiling information, purchase history, etc. As described above,because the unique ID may be replicated across local storage of severaldevices associated with the user, the ad or synchronizing servers 510may target ads based on a more complete picture of a user's demographicor behavioral history. For example, the unique ID stored in localstorage of the user's first device 502 may be replicated into localstorage of the user's second device 504.

Accordingly, when the same user uses the second device 504 to access webpages using the same unique ID, the ad or synchronizing servers 510 mayaccess information and data collected with respect to the user's use ofthe first device when determining which content and advertising toserver to the user. Specifically, the user's second device 504 may (1)request a web page or ad from an ad or publisher server 508; and (2)receive HTTP and an ad tag from the ad or publisher server 508. Theuser's second device 504 may execute the ad tag, such as by executingany type of client side script (e.g., JavaScript) to (3A) look-up aunique ID stored on the device. As described above, the unique ID may bestored within local storage associated with a browser of the seconddevice 504. The user's second device 504 may then (4A) issue an adrequest to ad or synchronizing servers 510, where the request includesthe looked-up unique ID. As an alternative to transmitting the unique IDin an ad request, the user device 504 may (3B) set a cookie containingthe unique ID in location storage, and then (4B) issue an ad request toad or synchronizing servers 510, where the ad request includes cookiedata that may or may not include the unique ID. In one embodiment, theset cookie may include another type of advertising identifier that iscross-referenced to the user through the unique ID. Because the uniqueID may be replicated across local storage of several devices associatedwith the user, the ad or synchronizing servers 510 may target ads basedon a more complete picture of a user's demographic or behavioralhistory.

For example, the ad or synchronizing server(s) 510 may determine, basedon the demographic or browsing history information generated from theuser's use of the first device, an advertisement to display to the userduring the user's use of a second device. Specifically, when a user usesa second device to request web content, e.g., from a publisher server112, the user's second device may also request an ad from an ad server152. Because the user's second device may send an ad request containingthe user's unique identifier or instance identifier, the ad servers 152and/or synchronizing processor 154 may again lookup demographic orbrowsing history information generated from the user's use of a firstdevice. For example, the ad server 152 and/or synchronizing processor154 may search databases 156 for the unique identifier and/or instanceidentifier to find indexed browsing history, demographic data,behavioral information, user profiling information, purchase history,etc. The stored historical data may be data generated from the user'sfirst device or any other device having local storage containing theunique identifier and/or instance identifier. As a result, the adservers 152 and/or synchronizing processor 154 may be able to serve adson the user's device based on one or more of: browsing history,demographic data, behavioral information, user profiling information,purchase history, any or all of which may be based on data collectedfrom more than one device used by the user.

User activity by which users access the Internet, as depicted in FIGS. 1and 2, may be considered to be one channel of user activity. Other typeof activity, such as placing or receiving telephone calls using mobiledevice 102, as depicted in FIG. 1, may be considered to be a differentchannel of user activity. According to one or embodiments, activity inone channel may be used to serve ads on a user's device in a differentchannel. For example, a user's Internet activity such as, for example,browsing history, demographic data, behavioral information, userprofiling information, purchase history, etc., may be used to serve adson a user's mobile device when placing or receiving a telephone call.FIG. 6 depicts a flowchart of a method of providing targeted contentacross user channels, according to one or more embodiments.

As shown in FIG. 6, at operation 610, synchronizing server 150 maycreate a device activity campaign. At operation 620, synchronizingserver 150 may run the device activity campaign on a cross-channel eventproducer application, which may be run on a user device, such as one ofuser devices 102-110 depicted in FIGS. 1 and 2. At operation 630,synchronizing server 150 may store device activity events received fromcross-channel event producer application. At operation 640,synchronizing server 150 may create an audience population based on thestored device activity events. At operation 650, synchronizing server150 may determine links for additional secondary user devices, such asone or more of user devices 102-110 depicted in FIGS. 1 and 2. Links foradditional secondary user devices may be determined, for example, bymethod 300 depicted in FIG. 3 and discussed in detail above. Atoperation 660, synchronizing server 150 may create a cross-channeladvertising campaign targeting the audience population. Thecross-channel advertising campaign may be created, for example, bymethod 400 depicted in FIG. 4 and discussed in detail above. Atoperation 670, synchronizing server 150 may run the cross-channeladvertising campaign based on the device activity and the determinedadditional secondary user devices.

The cross-channel advertising campaign may target ads displayed on thesecondary user devices, such as Internet connected user devices, basedon telephone calls placed or received on a user's mobile device orsmartphone. Alternatively, advertisements may be displayed during theuser's telephone call based on the connected telephone number and/or theuser's Internet activity on the user's mobile device or smartphone orthe determined additional secondary user devices. For example, asadvertisement or targeted message may be displayed on a caller ID screenof the user's mobile device or smartphone, as depicted in FIGS. 8A-C. Asshown in FIGS. 8A-C, an advertisement or targeted message displayed on acaller ID screen of the user's mobile device or smartphone may be, forexample, text-based (FIG. 8A), informative (FIG. 8B), or interactive(FIG. 8C). A text-based advertisement or targeted message, as shown inFIG. 8A, may include only text elements. An informative advertisement ortargeted message, as shown in FIG. 8B, may further include graphicalelements or other elements that may provide richer information to theuser. An interactive advertisement or targeted message, as shown in FIG.8C, may further include user interface elements that may allow the userto interact with the message to convey information to the advertiser ororiginator of the advertisement or targeted message. An advertisement ortargeted message, such as depicted in FIGS. 8A-C may be sent inconnection with an existing transaction with a customer, such as, forexample, confirming an appointment or scheduling a delivery. However, anadvertisement or targeted message may also be sent to a user who is notan existing customer. For example, an advertiser, or other contentprovider, may provide a list of telephone numbers and information,possibly including graphics and/or text messages, to be displayed to theuser. Based on events recorded during such a call, digital retargetingadvertisements may be run according to the user information anddetermined additional secondary user devices.

Alternatively, an advertisement or targeted message may be displayed ona dialer screen of a user's mobile device or smartphone. Such anadvertisement or targeted message may be displayed in response to aphone number dialed by the user, selected from a contacts list, accessedwithin an email or other message, or accessed within a web site or othercontent displayed on a user device, for example. Such an advertisementor targeted message may further include user interface elements allowingthe user to interact with the message to convey information to theadvertiser or originator of the advertisement or targeted message, or toinitiate further interaction with the advertiser or originator of theadvertisement or targeted message. For example, user interface elementsmay allow the user to initiate interaction with a merchant's automatedcustomer support system.

The advertisement or targeted message may include identifyinginformation 810, such as, for example, a name and phone number of acalling business, a text message 820, and graphic content 840. Textmessage 820 may be provided by the business originating the incomingcall and may relate to the nature of the call, such as, for example,confirming an upcoming appointment. Graphic content 840 may be, forexample, an image, a drawing, an animation, or a video, etc., and may bean advertising image provided by the business originating the incomingcall. Alternatively, graphic content 840 may be related to an advertiserother than the originator of the phone call and may be provided based onthe user's Internet activity on the determined additional secondary userdevices. The advertisement or targeted message may further include aninteractive portion 860, which may include buttons or other userinterface elements that may allow the user to interact with theadvertiser without answering the phone call.

FIG. 7 illustrates a high-level functional block diagram of an exemplarydevice 700, in which embodiments of the present disclosure, or portionsthereof, may be implemented, e.g., as computer-readable code. Forexample, each of the exemplary systems, user interfaces and methodsdescribed above with respect to FIGS. 1-5 can be implemented in device700 using hardware, software, firmware, tangible computer readable mediahaving instructions stored thereon, or a combination thereof and may beimplemented in one or more computer systems or other processing systems.Hardware, software, or any combination of such may implement each of theexemplary systems, user interfaces and methods described above withrespect to FIGS. 1-6 and 8.

If programmable logic is used, such logic may execute on a commerciallyavailable processing platform or a special purpose device. One ofordinary skill in the art may appreciate that embodiments of thedisclosed subject matter can be practiced with various computer systemconfigurations, including multi-core multiprocessor systems,minicomputers, mainframe computers, computer linked or clustered withdistributed functions, as well as pervasive or miniature computers thatmay be embedded into virtually any device.

For instance, at least one processor device and a memory may be used toimplement the above described embodiments. A processor device may be asingle processor, a plurality of processors, or combinations thereof.Processor devices may have one or more processor “cores.”

Various embodiments of the present disclosure, as described above in theexamples of FIGS. 1-6 and 8 may be implemented using device 700. Afterreading this description, it will become apparent to a person skilled inthe relevant art how to implement embodiments of the present disclosureusing other computer systems and/or computer architectures. Althoughoperations may be described as a sequential process, some of theoperations may in fact be performed in parallel, concurrently, and/or ina distributed environment, and with program code stored locally orremotely for access by single or multi-processor machines. In addition,in some embodiments the order of operations may be rearranged withoutdeparting from the spirit of the disclosed subject matter.

As shown in FIG. 7, device 700 may include a central processing unit(CPU) 720. CPU 720 may be any type of processor device including, forexample, any type of special purpose or a general purpose microprocessordevice. As will be appreciated by persons skilled in the relevant art,CPU 720 also may be a single processor in a multi-core/multiprocessorsystem, such system operating alone, or in a cluster of computingdevices operating in a cluster or server farm. CPU 720 may be connectedto a data communication infrastructure 710, for example, a bus, messagequeue, network, or multi-core message-passing scheme.

Device 700 may also include a main memory 740, for example, randomaccess memory (RAM), and may also include a secondary memory 730.Secondary memory 730, e.g., a read-only memory (ROM), may be, forexample, a hard disk drive or a removable storage drive. Such aremovable storage drive may comprise, for example, a floppy disk drive,a magnetic tape drive, an optical disk drive, a flash memory, or thelike. The removable storage drive in this example reads from and/orwrites to a removable storage unit in a well-known manner. The removablestorage unit may comprise a floppy disk, magnetic tape, optical disk,etc. which is read by and written to by the removable storage drive. Aswill be appreciated by persons skilled in the relevant art, such aremovable storage unit generally includes a computer usable storagemedium having stored therein computer software and/or data.

In alternative implementations, secondary memory 730 may include othersimilar means for allowing computer programs or other instructions to beloaded into device 700. Examples of such means may include a programcartridge and cartridge interface (such as that found in video gamedevices), a removable memory chip (such as an EPROM, or PROM) andassociated socket, and other removable storage units and interfaces,which allow software and data to be transferred from a removable storageunit to device 700.

Device 700 may also include a communications interface (“COM”) 760.Communications interface 760 allows software and data to be transferredbetween device 700 and external devices. Communications interface 760may include a modem, a network interface (such as an Ethernet card), acommunications port, a PCMCIA slot and card, or the like. Software anddata transferred via communications interface 760 may be in the form ofsignals, which may be electronic, electromagnetic, optical, or othersignals capable of being received by communications interface 760. Thesesignals may be provided to communications interface 760 via acommunications path of device 700, which may be implemented using, forexample, wire or cable, fiber optics, a phone line, a cellular phonelink, an RF link or other communications channels.

The hardware elements, operating systems and programming languages ofsuch equipment are conventional in nature, and it is presumed that thoseskilled in the art are adequately familiar therewith. Device 700 alsomay include input and output ports 750 to connect with input and outputdevices such as keyboards, mice, touchscreens, monitors, displays, etc.Of course, the various server functions may be implemented in adistributed fashion on a number of similar platforms, to distribute theprocessing load. Alternatively, the servers may be implemented byappropriate programming of one computer hardware platform.

Other embodiments of the disclosure will be apparent to those skilled inthe art from consideration of the specification and practice of theinvention disclosed herein. It is intended that the specification andexamples be considered as exemplary only, with a true scope and spiritof the invention being indicated by the following claims.

What is claimed is:
 1. A method of providing targeted content acrossuser channels, the method comprising: receiving a plurality of deviceactivity events on a user device; storing the received plurality ofdevice activity events; creating an audience population based on thestored device activity events; determining links for additionalsecondary user devices based on the user device; creating across-channel advertising campaign targeting the determined audiencepopulation; and running the cross-channel advertising campaign based onthe device activity and the determined additional secondary userdevices.
 2. The method of claim 1, wherein the cross-channel advertisingcampaign comprises targeted content displayed on a user's device when atelephone call is received or placed.
 3. The method of claim 2, whereinthe targeted content comprises one or more of a textual message,graphical elements, and user interface elements allowing the user toconvey information to the originator of the targeted message.
 4. Themethod of claim 2, wherein the targeted content is sent in connection toa previous transaction between the user and the originator of thetargeted message.
 5. The method of claim 2, wherein the originator ofthe targeted message is not a party to the telephone call.
 6. The methodof claim 1, the method further comprising: creating a device activitycampaign; and running the device activity campaign on the user device.7. The method of claim 6, wherein the device activity campaign is run ona cross-channel event producer application on the user device.
 8. Anon-transitory computer readable medium storing a program causing acomputer to execute a method of providing targeted content across userchannels, the method comprising: receiving a plurality of deviceactivity events on a user device; storing the received plurality ofdevice activity events; creating an audience population based on thestored device activity events; determining links for additionalsecondary user devices based on the user device; creating across-channel advertising campaign targeting the determined audiencepopulation; and running the cross-channel advertising campaign based onthe device activity and the determined additional secondary userdevices.
 9. The non-transitory computer readable medium of claim 8,wherein the cross-channel advertising campaign comprises targetedcontent displayed on a user's device when a telephone call is receivedor placed.
 10. The non-transitory computer readable medium of claim 9,wherein the targeted content comprises one or more of a textual message,graphical elements, and user interface elements allowing the user toconvey information to the originator of the targeted message.
 11. Thenon-transitory computer readable medium of claim 9, wherein the targetedcontent is sent in connection to a previous transaction between the userand the originator of the targeted message.
 12. The non-transitorycomputer readable medium of claim 9, wherein the originator of thetargeted message is not a party to the telephone call.
 13. Thenon-transitory computer readable medium of claim 8, the method furthercomprising: creating a device activity campaign; and running the deviceactivity campaign on the user device.
 14. The non-transitory computerreadable medium of claim 13, wherein the device activity campaign is runon a cross-channel event producer application on the user device.
 15. Acomputer system for providing targeted content across user channels, thesystem comprising: a memory having processor-readable instructionsstored therein; and a processor configured to access the memory andexecute the processor-readable instructions, which when executed by theprocessor configures the processor to perform a plurality of functions,including functions to: receive a plurality of device activity events ona user device; store the received plurality of device activity events;creating an audience population based on the stored device activityevents; determine links for additional secondary user devices based onthe user device; create a cross-channel advertising campaign targetingthe determined audience population; and run the cross-channeladvertising campaign based on the device activity and the determinedadditional secondary user devices.
 16. The computer system of claim 15,wherein the cross-channel advertising campaign comprises targetedcontent displayed on a user's device when a telephone call is receivedor placed.
 17. The computer system of claim 16, wherein the targetedcontent comprises one or more of a textual message, graphical elements,and user interface elements allowing the user to convey information tothe originator of the targeted message.
 18. The computer system of claim16, wherein the targeted content is sent in connection to a previoustransaction between the user and the originator of the targeted message.19. The computer system of claim 15, wherein the plurality of functionsperformed by the processor when executing the processor-readableinstructions further includes functions to: creating a device activitycampaign; and running the device activity campaign on the user device.20. The computer system of claim 19, wherein the device activitycampaign is run on a cross-channel event producer application on theuser device.